Dataset: An empirical study on self-admitted technical debt in modern code review

This data was used in the IST paper "An Empirical Study on Self-Admitted Technical Debt in Modern Code Review". The program to use this data is published in GitHub (https://github.com/Yutaro-Kashiwa/ReviewSATD_RP) When you use this data in your research, please cite the following papers: ``` @article{Kashiwa:IST:2022:SATD_Review, author = {Yutaro Kashiwa and Ryoma Nishikawa and Yasutaka Kamei and Masanari Kondo and Emad Shihab and Ryosuke Sato and Naoyasu Ubayashi}, title = {An empirical study on self-admitted technical debt in modern code review}, journal = {Information and Software Technology}, volume = {146}, pages = {106855}, year = {2022}, url = {https://doi.org/10.1016/j.infsof.2022.106855}, doi = {10.1016/j.infsof.2022.106855} } ``

What Are the Perception Gaps Between FLOSS Developers and SE Researchers?

Part 2: Organizational Aspects of FLOSS ProjectsInternational audienceIn recent years, many researchers in the SE community have been devoting considerable efforts to provide FLOSS developers with a means to quickly find and fix various kinds of bugs in FLOSS products such as security and performance bugs. However, it is not exactly sure how FLOSS developers think about bugs to be removed preferentially. Without a full understanding of FLOSS developers’ perceptions of bug finding and fixing, researchers’ efforts might remain far away from FLOSS developers’ needs. In this study, we interview 322 notable GitHub developers about high impact bugs to understand FLOSS developers’ needs for bug finding and fixing, and we manually inspect and classify developers’ answers (bugs) by symptoms and root causes of bugs. As a result, we show that security and breakage bugs are highly crucial for FLOSS developers. We also identify what kinds of high impact bugs should be studied newly by the SE community to help FLOSS developers